When your workflow template contains a Copy Data Object policy in which the source and target data objects are the same, you might encounter issues with SAS Workflow Services. When executing the policy, SAS Workflow Services copies the value of the data object to itself. This copy action generates another invocation of the same policy. As a result, the data object is updated continuously in an endless loop. When the looping condition occurs, you might see one or more of the following problems:

• The ActiveMQ log file shows that the WorkflowEventsQueue is at 100% capacity. 
• The number of logs that reside in the SAS-configuration-file\Lev1\Web\activemq\data\kahadb directory grows over time, causing disk space to fill up.
• Transitions between workflow tasks take longer than expected and worsen over time. SAS Workflow Services might eventually become unresponsive.

To prevent the issue for new workflow instances, remove the Copy Data Object policy. After you remove the policy and activate the corrected workflow template, you might need to clean up disk space. Follow the instructions in SAS Note 52315, "Increasing numbers of Apache ActiveMQ journal log files in certain SAS^® 9.4 Enterprise BI and SAS® Visual Analytics environments fill up disk space."

You might encounter this issue if you use SAS^® Anti-Money Laundering and your workflow template is based on the FCFWorkflow template that is provided with the SAS^® solution. To fix the template, follow the instructions in SAS Note 62533, "A workflow template in SAS^® Anti-Money Laundering causes utilization issues with SAS^® Workflow Services and Apache ActiveMQ."

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Middle Tier 9.4_M5 is available at:

A fix for this issue for SAS Middle Tier 9.4_M4 is available at:

A fix for this issue for SAS Middle Tier 9.4_M3 is available at: